Exchanging a message including drone-coupled capability information between a drone-coupled user equipment and a component of a terrestrial wireless communication subscriber network

ABSTRACT

In an embodiment, a drone-coupled UE transmits a message to a network component (e.g., eNB) of a terrestrial wireless communication subscriber network that identifies a drone-coupled capability information of the drone-coupled UE, the drone-coupled capability information being configured to indicate, to the network component, that the drone-coupled UE is capable of engaging in a flying state. The network component receives the message and determines that the drone-coupled UE is capable of engaging in a flying state based on the received message.

CROSS-REFERENCE TO RELATED APPLICATION

The present Application for Patent claims the benefit of U.S.Provisional Application No. 62/501,054, entitled “MANAGING DRONE-COUPLEDUSER EQUIPMENTS”, filed May 3, 2017, assigned to the assignee hereof andhereby expressly incorporated by reference herein in its entirety.

BACKGROUND 1. Field of the Disclosure

Embodiments relate to exchanging a message including drone-coupledcapability information between a drone-coupled user equipment and acomponent of a terrestrial wireless communication subscriber network.

2. Description of the Related Art

User equipments (UEs), such as phones, tablet computers, desktopcomputers or laptop computers, are generally configured to connect toterrestrial wireless communication subscriber networks (e.g., 3G, 4G, 5GLTE, 5G New Radio (NR), etc.) with the expectation that the UEs are notairborne. For example, users are typically asked to place theirrespective UEs into “airplane” mode between takeoff and landing forcommercial flights, which restricts the UEs' capability for connectingto terrestrial wireless communication subscriber networks.

For most manned (or piloted) aerial vehicles, typical cruising altitudesand/or speeds make connections to terrestrial wireless communicationsubscriber networks impractical. For example, commercial aircraft mayreach cruising altitudes near 12 km at speeds between 800-1000 km/hr.Instead of relying upon terrestrial wireless communication subscribernetworks to support communications for/with manned aerial vehicles suchas commercial aircraft, most countries allocate a portion of Very HighFrequency (VHF) radio spectrum to define an Airband or Aircraft bandthat is dedicated to radio-navigational communications and/or airtraffic control communications.

Regulatory agencies are increasingly authorizing deployment of unmannedaerial vehicles (UAVs), such as commercial drones. Commercial drones arebeing considered to provide a variety of services, such as packagedelivery, search-and-rescue, monitoring of critical infrastructure,wildlife conservation, flying cameras, surveillance, and so on.Commercial drones may operate at altitudes and speeds that are moresuitable for connections to terrestrial wireless communicationsubscriber networks. For example, in certain environments, commercialdrones may operate at cruising altitudes near 100 m at speeds up to ornear 160 km/h. However, uplink signals from commercial drones that arein-flight generally create more interference to terrestrial basestations compared to “grounded” UEs in a non-flying state.

SUMMARY

An embodiment is directed to a method of operating a drone-coupled userequipment (UE), including transmitting a message to a network componentof a terrestrial wireless communication subscriber network thatidentifies a drone-coupled capability information of the drone-coupledUE, the drone-coupled capability information being configured toindicate, to the network component, that the drone-coupled UE is capableof engaging in a flying state.

Another embodiment is directed to a method of operating a networkcomponent of a terrestrial wireless communication subscriber network,including receiving a message from a drone-coupled user equipment (UE)that identifies a drone-coupled capability information of thedrone-coupled UE, and determining that the drone-coupled UE is capableof engaging in a flying state based on the received message.

Another embodiment is directed to a drone-coupled user equipment (UE),comprising at least one processor coupled to a memory and a wirelesscommunications interface and configured to transmit a message to anetwork component of a terrestrial wireless communication subscribernetwork that identifies a drone-coupled capability information of thedrone-coupled UE, the drone-coupled capability information beingconfigured to indicate, to the network component, that the drone-coupledUE is capable of engaging in a flying state.

Another embodiment is directed to a network component of a terrestrialwireless communication subscriber network, comprising at least oneprocessor coupled to a memory and at least one communications interfaceand configured to receive a message from a drone-coupled user equipment(UE) that identifies a drone-coupled capability information of thedrone-coupled UE, and determine that the drone-coupled UE is capable ofengaging in a flying state based on the received message.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of embodiments of the disclosure will bereadily obtained as the same becomes better understood by reference tothe following detailed description when considered in connection withthe accompanying drawings which are presented solely for illustrationand not limitation of the disclosure, and in which:

FIG. 1 illustrates a high-level system architecture of a wirelesscommunications system in accordance with an embodiment of thedisclosure.

FIG. 2A illustrates a user equipment (UE) in accordance with anembodiment of the disclosure.

FIG. 2B illustrates the UE of FIG. 2A deployed within a drone inaccordance with an embodiment of the disclosure.

FIG. 3 illustrates a network component in accordance with an embodimentof the disclosure.

FIG. 4 illustrates a communications device that includes structuralcomponents in accordance with an embodiment of the disclosure.

FIG. 5 illustrates a server in accordance with an embodiment of thedisclosure.

FIG. 6 illustrates interference caused by uplink signals from commercialdrones that are in-flight relative to “grounded” UEs in a non-flyingstate.

FIG. 7 illustrates an authorized commercial drone and an unauthorizeddrone.

FIGS. 8-9 illustrate procedures by which a drone-coupled capabilityinformation of a drone-coupled UE can be conveyed to a network componentof a terrestrial wireless communication subscriber network in accordancewith embodiments of the disclosure.

FIG. 10A illustrates a process by which a drone-coupled UE conveys amessage indicative of in-flight status in accordance with an embodimentof the disclosure.

FIG. 10B illustrates a process by which a network component receives amessage indicative of in-flight status for a drone-coupled UE inaccordance with an embodiment of the disclosure.

FIG. 11A illustrates a process of selectively implementing a flyingstate protocol or a non-flying state protocol for a drone-coupled UE inaccordance with an embodiment of the disclosure.

FIG. 11B illustrates a drone-coupled UE handing off directly betweenbase stations while skipping or bypassing an intervening base station inaccordance with an embodiment of the disclosure.

FIG. 12A illustrates an example implementation of the process of FIG.11A in accordance with an embodiment of the disclosure.

FIG. 12B illustrates a more detailed implementation of the process ofFIG. 12A in accordance with an embodiment of the disclosure.

FIG. 13 illustrates a process by which a network component of aterrestrial wireless communication subscriber network conveys anavailable support status for drone-related service in accordance with anembodiment of the disclosure.

FIG. 14 illustrates a process by which a drone-coupled UE determineswhether to request service (and/or how much service to request) from aterrestrial wireless communication subscriber network in accordance withan embodiment of the disclosure.

FIG. 15 illustrates an example implementation of the process of FIG. 14in accordance with an embodiment of the disclosure.

FIG. 16 illustrates an example implementation of the process of FIG. 14in accordance with another embodiment of the disclosure.

DETAILED DESCRIPTION

Embodiments of the disclosure relate to various methodologies formanaging drone-coupled user equipments (UEs).

Aspects of the disclosure are disclosed in the following description andrelated drawings directed to specific embodiments of the disclosure.Alternate embodiments may be devised without departing from the scope ofthe disclosure. Additionally, well-known elements of the disclosure willnot be described in detail or will be omitted so as not to obscure therelevant details of the disclosure.

The words “exemplary” and/or “example” are used herein to mean “servingas an example, instance, or illustration.” Any embodiment describedherein as “exemplary” and/or “example” is not necessarily to beconstrued as preferred or advantageous over other embodiments. Likewise,the term “embodiments of the disclosure” does not require that allembodiments of the disclosure include the discussed feature, advantageor mode of operation.

Further, many embodiments are described in terms of sequences of actionsto be performed by, for example, elements of a computing device. It willbe recognized that various actions described herein can be performed byspecific circuits (e.g., application specific integrated circuits(ASICs)), by program instructions being executed by one or moreprocessors, or by a combination of both. Additionally, these sequence ofactions described herein can be considered to be embodied entirelywithin any form of computer-readable storage medium having storedtherein a corresponding set of computer instructions that upon executionwould cause an associated processor to perform the functionalitydescribed herein. Thus, the various aspects of the disclosure may beembodied in a number of different forms, all of which have beencontemplated to be within the scope of the claimed subject matter. Inaddition, for each of the embodiments described herein, thecorresponding form of any such embodiments may be described herein as,for example, “logic configured to” perform the described action.

A client device, referred to herein as a user equipment (UE), may bemobile or stationary, and may communicate with a wired access networkand/or a radio access network (RAN). As used herein, the term “UE” maybe referred to interchangeably as an “access terminal” or “AT”, a“wireless device”, a “subscriber device”, a “subscriber terminal”, a“subscriber station”, a “user terminal” or UT, a “mobile device”, a“mobile terminal”, a “mobile station” and variations thereof. In anembodiment, UEs can communicate with a core network via the RAN, andthrough the core network the UEs can be connected with external networkssuch as the Internet. Of course, other mechanisms of connecting to thecore network and/or the Internet are also possible for the UEs, such asover wired access networks, WiFi networks (e.g., based on IEEE 802.11,etc.) and so on. UEs can be embodied by any of a number of types ofdevices including but not limited to cellular telephones, personaldigital assistants (PDAs), pagers, laptop computers, desktop computers,PC cards, compact flash devices, external or internal modems, wirelessor wireline phones, and so on. A communication link through which UEscan send signals to the RAN is called an uplink channel (e.g., a reversetraffic channel, a reverse control channel, an access channel, etc.). Acommunication link through which the RAN can send signals to UEs iscalled a downlink or forward link channel (e.g., a paging channel, acontrol channel, a broadcast channel, a forward traffic channel, etc.).A communication link through which UEs can send signals to other UEs iscalled a peer-to-peer (P2P) or device-to-device (D2D) channel.

FIG. 1 illustrates a high-level system architecture of a wirelesscommunications system 100 in accordance with an embodiment of thedisclosure. The wireless communications system 100 contains UEs 1 . . .N. For example, in FIG. 1, UEs 1 . . . 3 are illustrated as cellularcalling phones, UEs 1 . . . 6 are illustrated as cellular touchscreenphones or smart phones, and UE N is illustrated as a desktop computer orPC.

Referring to FIG. 1, UEs 1 . . . N are configured to communicate with anaccess network (e.g., a RAN 120, an access point 125, etc.) over aphysical communications interface or layer, shown in FIG. 1 as airinterfaces 104, 106, 108 and/or a direct wired connection. The airinterfaces 104 and 106 can comply with a given cellular communicationsprotocol (e.g., CDMA, EVDO, eHRPD, GSM, EDGE, W-CDMA, 4G LTE, 5G LTE, 5GNew Radio (NR), etc.), while the air interface 108 can comply with awireless IP protocol (e.g., IEEE 802.11). The RAN 120 may include aplurality of access points that serve UEs over air interfaces, such asthe air interfaces 104 and 106. The access points in the RAN 120 can bereferred to as access nodes or ANs, access points or APs, base stationsor BSs, Node Bs, eNBs, gNBs, and so on. These access points can beterrestrial access points (or ground stations), or satellite accesspoints. The RAN 120 may be configured to connect to a core network 140that can perform a variety of functions, including bridging circuitswitched (CS) calls between UEs served by the RAN 120 and other UEsserved by the RAN 120 or a different RAN altogether, and can alsomediate an exchange of packet-switched (PS) data with external networkssuch as Internet 175. As used herein, the RAN 120, the core network 140or a combination thereof may be referred to as a terrestrial wirelesscommunication subscriber network.

The Internet 175, in some examples includes a number of routing agentsand processing agents (not shown in FIG. 1 for the sake of convenience).In FIG. 1, UE N is shown as connecting to the Internet 175 directly(i.e., separate from the core network 140, such as over an Ethernetconnection of WiFi or 802.11-based network). The Internet 175 canthereby function to bridge packet-switched data communications betweenUEs 1 . . . N via the core network 140. Also shown in FIG. 1 is theaccess point 125 that is separate from the RAN 120. The access point 125may be connected to the Internet 175 independent of the core network 140(e.g., via an optical communications system such as FiOS, a cable modem,etc.). The air interface 108 may serve UE 5 or UE 6 over a localwireless connection, such as IEEE 802.11 in an example. UE N is shown asa desktop computer with a wired connection to the Internet 175, such asa direct connection to a modem or router, which can correspond to theaccess point 125 itself in an example (e.g., for a WiFi router with bothwired and wireless connectivity).

Referring to FIG. 1, a server 170 is shown as connected to the Internet175, the core network 140, or both. The server 170 can be implemented asa plurality of structurally separate servers, or alternately maycorrespond to a single server. The server 170 may correspond to any typeof server, such as a web server (e.g., hosting a web page), anapplication download server, or an application server that supportsparticular communicative service(s) such as IP Multimedia Subsystem(IMS) service, such as Voice-over-Internet Protocol (VoIP) sessions,Push-to-Talk (PTT) sessions, group communication sessions, socialnetworking services, etc.

Referring to FIG. 1, UEs 1 . . . 3 are depicted as part of a D2D networkor D2D group 185, with UEs 1 and 3 being connected to the RAN 120 viathe air interface 104. In an embodiment, UE 2 may also gain indirectaccess to the RAN 120 via mediation by UEs 1 and/or 3, whereby data‘hops’ to/from UE 2 and one (or more) of UEs 1 and 3, which communicatewith the RAN 120 on behalf of UE 2.

FIG. 2A illustrates a UE 200 in accordance with an embodiment of thedisclosure. The UE 200 includes one or more processors 205 (e.g., one ormore ASICs, one or more digital signal processors (DSPs), etc.) and amemory 210 (e.g., RAM, ROM, EEPROM, flash cards, or any memory common tocomputer platforms). The UE 200 also optionally includes one or more UIinput components 215 (e.g., a keyboard and mouse, a touchscreen, amicrophone, one or more buttons such as volume or power buttons, etc.)and one or more UI output components 220 (e.g., speakers, a displayscreen, a vibration device for vibrating the UE 200, etc.). In anexample, the UI input components 215 and UI output components 220 areoptional because the UE 200 need not interface with a local user in allimplementations. For example, if the UE 200 is implemented as a wirelesscommunications component of a commercial drone, the UE 200 may beinterfaced with via remote connections instead of a local UI interface.

The UE 200 further includes a wired communications interface 225 and awireless communications interface 230. In an example, the wiredcommunications interface 225 may be optional (e.g., commercial dronesmay be configured for wireless communication only). In an exampleembodiment, if made part of the UE 200, the wired communicationsinterface 225 can be used to support wired local connections toperipheral devices (e.g., a USB connection, a mini USB or lightningconnection, a headphone jack, graphics ports such as serial, VGA, HDMI,DVI or DisplayPort, audio ports, and so on) and/or to a wired accessnetwork (e.g., via an Ethernet cable or another type of cable that canfunction as a bridge to the wired access network such as HDMI v1.4 orhigher, etc.). In another example embodiment, the wirelesscommunications interface 230 includes one or more wireless transceiversfor communication in accordance with a local wireless communicationsprotocol (e.g., WLAN or WiFi, WiFi Direct, Bluetooth, etc.) and/or oneor more wireless transceivers for communication with a cellular RAN(e.g., via CDMA, W-CDMA, time division multiple access (TDMA), frequencydivision multiple access (FDMA), Orthogonal Frequency DivisionMultiplexing (OFDM), GSM, LTE, 4G, 5G LTE, 5G NR or other protocols thatmay be used in a terrestrial wireless communication subscriber network).The various components 205-230 of the UE 200 can communicate with eachother via a bus 235.

Referring to FIG. 2A, the UE 200 may correspond to any type of UE,including but not limited to a smart phone, a laptop computer, a desktopcomputer, a tablet computer, a wearable device (e.g., a pedometer, asmart watch, etc.), a communications component of a larger device (e.g.,a cellular module integrated into a commercial drone), and so on. Threeparticular implementation examples of the UE 200 are depicted in FIG.2A, which are illustrated as laptop 240, touchscreen device 255 (e.g., asmart phone, a tablet computer, etc.) and terrestrial wirelesscommunication subscriber network (e.g., cellular) module 290. The laptop240 includes a display screen 245 and a UI area 250 (e.g., keyboard,touchpad, power button, etc.), and while not shown the laptop 240 mayinclude various ports as well as wired and/or wireless transceivers(e.g., Ethernet card, WiFi card, broadband card, etc.).

The touchscreen device 255 is configured with a touchscreen display 260,peripheral buttons 265, 270, 275 and 280 (e.g., a power control button,a volume or vibrate control button, an airplane mode toggle button,etc.), and at least one front-panel button 285 (e.g., a Home button,etc.), among other components, as is known in the art. While not shownexplicitly as part of the touchscreen device 255, the touchscreen device255 can include one or more external antennas and/or one or moreintegrated antennas that are built into the external casing of thetouchscreen device 255, including but not limited to WiFi antennas,cellular antennas, satellite position system (SPS) antennas (e.g.,global positioning system (GPS) antennas), and so on.

The terrestrial wireless communication subscriber network (e.g.,cellular) module 290 is illustrated in FIG. 2A as a circuit coupled to aradio antenna. The terrestrial wireless communication subscriber network(e.g., cellular) module 290 may be integrated into a larger structure,such as a commercial drone, with the terrestrial wireless communicationsubscriber network (e.g., cellular) module 290 representing the UE (orcommunicative) component of the larger structure.

FIG. 2B illustrates a drone 200B in accordance with an embodiment of thedisclosure. The drone 200B, which may be a commercial drone that islicensed for at least some level of in-flight access to one or moreterrestrial wireless communication subscriber networks, includes variousflying hardware and flying control components (not shown), and iscoupled to the UE 200. The UE 200 in FIG. 2B may thereby alternativelybe referred to as a drone-coupled UE. In one example, the UE 200functions as a wireless communications component of the drone 200Bthrough which the drone 200B can establish a connection with the one ormore terrestrial wireless communication subscriber networks for whichin-flight access is authorized. In a further example, the UE 200 in thedrone 200B can be integrated with the flying control components of thedrone 200B in at least one embodiment (e.g., the processor(s) 205 and/ormemory 210 may support both the communications functionality of the UE200 as well as flying control).

Alternatively, the UE 200 may be coupled to the drone 200B physicallybut not communicatively. For example, a user may simply duct-tape the UE200 to the drone 200B so that the UE 200 may record and stream videowhile the drone 200B is flown and controlled completely independentlyfrom the UE 200. Hence, depending on how the UE 200 and drone 200B areconfigured, the UE 200 may be a drone-coupled UE in a physical sense, acommunicative sense, or both. Further, a physical coupling between theUE 200 and the drone 200B may be semi-permanent (e.g., the UE 200 is anintegrated physical component installed into the drone 200B, such as theterrestrial wireless communication subscriber network module 290), ortemporary (e.g., a user ties or tapes the UE 200 onto the drone 200B).

Moreover, as will be described below in more detail, the UE 200 may beconfigured to access the one or more terrestrial wireless communicationsubscriber networks while the drone 200B is in-flight, or alternativelywhen the drone 200B is not in-flight (i.e., grounded). In FIG. 2B, twoexample implementations of the drone 200B are shown. In particular, apackage-delivery drone 205B is shown carrying a package 210B, and asurveillance drone 215B is shown with an attached camera 220B.

FIG. 3 illustrates a network component 300 of a terrestrial wirelesscommunication subscriber network in accordance with an embodiment of thedisclosure. The network component 300 may be a component of the RAN 120(e.g., a base station, Node B, eNB, gNB, etc.), or alternatively may bea core network component of the terrestrial wireless communicationsubscriber network (e.g., a Mobility Management Entity (MME) of an LTEcore network, etc.). The network component 300 includes one or moreprocessors 305 (e.g., one or more ASICs, one or more DSPs, etc.) and amemory 310 (e.g., RAM, ROM, EEPROM, flash cards, or any memory common tocomputer platforms). The network component 300 further includes a wiredcommunications interface 325 and (optionally) a wireless communicationsinterface 330. In an example, the wireless communications interface 330may be optional if the network component 300 is implemented as a corenetwork component, which is essentially a network server. The variouscomponents 305-330 of the network component 300 can communicate witheach other via a bus 335. In an example embodiment, the wiredcommunications interface 325 can be used to connect to one or morebackhaul components.

In another example embodiment, the wireless communications interface 330(if made part of the network component 300) includes one or morewireless transceivers for communication in accordance with a wirelesscommunications protocol. The wireless communications protocol may bebased on the configuration of the network component 300. For example, ifthe network component 300 corresponds to an access point that isimplemented as a macro cell or a small cell (e.g., a femto cell, a picocell, etc.), the wireless communications interface 330 may include oneor more wireless transceivers configured to implement a cellularprotocol (e.g., CDMA, W-CDMA, GSM, 3G, 4G, 5G LTE, 5G NR, etc.). Inanother example, if the network component 300 is implemented as a WiFiAP (e.g., part of a WLAN, an Internet of Things (IoT) network, etc.),the wireless communications interface 330 may include one or morewireless transceivers configured to implement a WiFi (or 802.11)protocol (e.g., 802.11a, 802.11b, 802.11g, 802.11n, 802.11ax, etc.).

FIG. 4 illustrates a communications device 400 that includes structuralcomponents in accordance with an embodiment of the disclosure. Thecommunications device 400 can correspond to any of the above-notedcommunications devices, including but not limited to UE 200 or networkcomponent 300, any component included in the RAN 120 such as basestations, access points, eNBs, gNBs, BSCs or RNCs, any component of thecore network 140, any component coupled to the Internet 175 (e.g., theserver 170), and so on. Thus, communications device 400 can correspondto any electronic device that is configured to communicate with (orfacilitate communication with) one or more other entities over thewireless communications system 100 of FIG. 1.

Referring to FIG. 4, the communications device 400 includes transceivercircuitry configured to receive and/or transmit information 405. In anexample, if the communications device 400 corresponds to a wirelesscommunications device (e.g., UE 200), the transceiver circuitryconfigured to receive and/or transmit information 405 can include awireless communications interface (e.g., LTE, 5G NR, Bluetooth, WiFi,WiFi Direct, LTE-Direct, etc.) such as a wireless transceiver andassociated hardware (e.g., an RF antenna, a MODEM, a modulator and/ordemodulator, etc.). In another example, the transceiver circuitryconfigured to receive and/or transmit information 405 can correspond toa wired communications interface (e.g., a serial connection, a USB orFirewire connection, an Ethernet connection through which the Internet175 can be accessed, etc.). Thus, if the communications device 400corresponds to some type of network-based server (e.g., the server 170),the transceiver circuitry configured to receive and/or transmitinformation 405 can correspond to an Ethernet card, in an example, thatconnects the network-based server to other communication entities via anEthernet protocol. In a further example, the transceiver circuitryconfigured to receive and/or transmit information 405 can includesensory or measurement hardware by which the communications device 400can monitor its local environment (e.g., an accelerometer, a temperaturesensor, a light sensor, an antenna for monitoring local RF signals,etc.). The transceiver circuitry configured to receive and/or transmitinformation 405 can also include software that, when executed, permitsthe associated hardware of the transceiver circuitry configured toreceive and/or transmit information 405 to perform its reception and/ortransmission function(s). However, the transceiver circuitry configuredto receive and/or transmit information 405 does not correspond tosoftware alone, and the transceiver circuitry configured to receiveand/or transmit information 405 relies at least in part upon structuralhardware to achieve its functionality. Moreover, the transceivercircuitry configured to receive and/or transmit information 405 may beimplicated by language other than “receive” and “transmit”, so long asthe underlying function corresponds to a receive or transmit function.For example, functions such as obtaining, acquiring, retrieving,measuring, etc., may be performed by the transceiver circuitryconfigured to receive and/or transmit information 405 in certaincontexts as being specific types of receive functions. In anotherexample, functions such as sending, delivering, conveying, forwarding,etc., may be performed by the transceiver circuitry configured toreceive and/or transmit information 405 in certain contexts as beingspecific types of transmit functions. Other functions that correspond toother types of receive and/or transmit functions may also be performedby the transceiver circuitry configured to receive and/or transmitinformation 405.

Referring to FIG. 4, the communications device 400 further includes atleast one processor configured to process information 410. Exampleimplementations of the type of processing that can be performed by theat least one processor configured to process information 410 includesbut is not limited to performing determinations, establishingconnections, making selections between different information options,performing evaluations related to data, interacting with sensors coupledto the communications device 400 to perform measurement operations,converting information from one format to another (e.g., betweendifferent protocols such as .wmv to .avi, etc.), and so on. For example,the at least one processor configured to process information 410 caninclude a general purpose processor, a DSP, an ASIC, a fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the at least one processor configured to processinformation 410 may be any conventional processor, controller,microcontroller, or state machine. A processor may also be implementedas a combination of computing devices (e.g., a combination of a DSP anda microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration). The at least one processor configured to processinformation 410 can also include software that, when executed, permitsthe associated hardware of the at least one processor configured toprocess information 410 to perform its processing function(s). However,the at least one processor configured to process information 410 doesnot correspond to software alone, and the at least one processorconfigured to process information 410 relies at least in part uponstructural hardware to achieve its functionality. Moreover, the at leastone processor configured to process information 410 may be implicated bylanguage other than “processing”, so long as the underlying functioncorresponds to a processing function. For example, functions such asevaluating, determining, calculating, identifying, etc., may beperformed by the at least one processor configured to processinformation 410 in certain contexts as being specific types ofprocessing functions. Other functions that correspond to other types ofprocessing functions may also be performed by the at least one processorconfigured to process information 410.

Referring to FIG. 4, the communications device 400 further includesmemory configured to store information 415. In an example, the memoryconfigured to store information 415 can include at least anon-transitory memory and associated hardware (e.g., a memorycontroller, etc.). For example, the non-transitory memory included inthe memory configured to store information 415 can correspond to RAM,flash memory, ROM, erasable programmable ROM (EPROM), EEPROM, registers,hard disk, a removable disk, a CD-ROM, or any other form of storagemedium known in the art. The memory configured to store information 415can also include software that, when executed, permits the associatedhardware of the memory configured to store information 415 to performits storage function(s). However, the memory configured to storeinformation 415 does not correspond to software alone, and the memoryconfigured to store information 415 relies at least in part uponstructural hardware to achieve its functionality. Moreover, the memoryconfigured to store information 415 may be implicated by language otherthan “storing”, so long as the underlying function corresponds to astoring function. For example, functions such as caching, maintaining,etc., may be performed by the memory configured to store information 415in certain contexts as being specific types of storing functions. Otherfunctions that correspond to other types of storing functions may alsobe performed by the memory configured to store information 415.

Referring to FIG. 4, the communications device 400 further optionallyincludes user interface output circuitry configured to presentinformation 420. In an example, the user interface output circuitryconfigured to present information 420 can include at least an outputdevice and associated hardware. For example, the output device caninclude a video output device (e.g., a display screen, a port that cancarry video information such as USB, HDMI, etc.), an audio output device(e.g., speakers, a port that can carry audio information such as amicrophone jack, USB, HDMI, etc.), a vibration device and/or any otherdevice by which information can be formatted for output or actuallyoutputted by a user or operator of the communications device 400. Forexample, if the communications device 400 corresponds to the laptop 240or touchscreen device 255 as shown in FIG. 2A, the user interface outputcircuitry configured to present information 420 can include a displaysuch as display screen 245 or touchscreen display 260. In a furtherexample, the user interface output circuitry configured to presentinformation 420 can be omitted for certain communications devices, suchas certain UEs (e.g., terrestrial wireless communication subscribernetwork module 290) and/or network communications devices that do nothave a local user (e.g., network switches or routers, remote servers,etc.). The user interface output circuitry configured to presentinformation 420 can also include software that, when executed, permitsthe associated hardware of the user interface output circuitryconfigured to present information 420 to perform its presentationfunction(s). However, the user interface output circuitry configured topresent information 420 does not correspond to software alone, and theuser interface output circuitry configured to present information 420relies at least in part upon structural hardware to achieve itsfunctionality. Moreover, the user interface output circuitry configuredto present information 420 may be implicated by language other than“presenting”, so long as the underlying function corresponds to apresenting function. For example, functions such as displaying,outputting, prompting, conveying, etc., may be performed by the userinterface output circuitry configured to present information 420 incertain contexts as being specific types of presenting functions. Otherfunctions that correspond to other types of presenting functions mayalso be performed by the user interface output circuitry configured topresent information 420.

Referring to FIG. 4, the communications device 400 further optionallyincludes user interface input circuitry configured to receive local userinput 425. In an example, the user interface input circuitry configuredto receive local user input 425 can include at least a user input deviceand associated hardware. For example, the user input device can includebuttons, a touchscreen display, a keyboard, a camera, an audio inputdevice (e.g., a microphone or a port that can carry audio informationsuch as a microphone jack, etc.), and/or any other device by whichinformation can be received from a user or operator of thecommunications device 400. For example, if the communications device 400corresponds to laptop 240 or touchscreen device 255 as shown in FIG. 2A,the user interface input circuitry configured to receive local UI area250 or touchscreen display 260, etc. In a further example, the userinterface input circuitry configured to receive local user input 425 canbe omitted for certain communications devices, such as certain UEs(e.g., terrestrial wireless communication subscriber network module 290)and/or network communications devices that do not have a local user(e.g., network switches or routers, remote servers, etc.). The userinterface input circuitry configured to receive local user input 425 canalso include software that, when executed, permits the associatedhardware of the user interface input circuitry configured to receivelocal user input 425 to perform its input reception function(s).However, the user interface input circuitry configured to receive localuser input 425 does not correspond to software alone, and the userinterface input circuitry configured to receive local user input 425relies at least in part upon structural hardware to achieve itsfunctionality. Moreover, the user interface input circuitry configuredto receive local user input 425 may be implicated by language other than“receiving local user input”, so long as the underlying functioncorresponds to a receiving local user function. For example, functionssuch as obtaining, receiving, collecting, etc., may be performed by theuser interface input circuitry configured to receive local user input425 in certain contexts as being specific types of receiving local userfunctions. Other functions that correspond to other types of receivinglocal user input functions may also be performed by the user interfaceinput circuitry configured to receive local user input 425.

Referring to FIG. 4, while the configured structural components of 405through 425 are shown as separate or distinct blocks in FIG. 4 that areimplicitly coupled to each other via an associated communication bus(not shown expressly), it will be appreciated that the hardware and/orsoftware by which the respective configured structural components of 405through 425 performs their respective functionality can overlap in part.For example, any software used to facilitate the functionality of theconfigured structural components of 405 through 425 can be stored in thenon-transitory memory associated with the memory configured to storeinformation 415, such that the configured structural components of 405through 425 each performs their respective functionality (i.e., in thiscase, software execution) based in part upon the operation of softwarestored by the memory configured to store information 415. Likewise,hardware that is directly associated with one of the configuredstructural components of 405 through 425 can be borrowed or used byother of the configured structural components of 405 through 425 fromtime to time. For example, the at least one processor configured toprocess information 410 can format data into an appropriate formatbefore being transmitted by the transceiver circuitry configured toreceive and/or transmit information 405, such that the transceivercircuitry configured to receive and/or transmit information 405 performsits functionality (i.e., in this case, transmission of data) based inpart upon the operation of structural hardware associated with the atleast one processor configured to process information 410.

The various embodiments may be implemented on any of a variety ofcommercially available server devices, such as server 500 illustrated inFIG. 5. In an example, the server 500 may correspond to one exampleconfiguration of the server 170 or the network component 300 (e.g., ifimplemented as a core network component) as described above. In FIG. 5,the server 500 includes a processor 501 coupled to volatile memory 502and a large capacity nonvolatile memory, such as a disk drive 503. Theserver 500 may also include a floppy disc drive, compact disc (CD) orDVD disc drive 506 coupled to the processor 501. The server 500 may alsoinclude network access ports 504 coupled to the processor 501 forestablishing data connections with a network 507, such as a local areanetwork coupled to other broadcast system computers and servers or tothe Internet. In context with FIG. 4, it will be appreciated that theserver 500 of FIG. 5 illustrates one example implementation of thecommunications device 400, whereby the transceiver circuitry configuredto transmit and/or receive information 405 corresponds to the networkaccess ports 504 used by the server 500 to communicate with the network507, the at least one processor configured to process information 410corresponds to the processor 501, and the memory configuration to storeinformation 415 corresponds to any combination of the volatile memory502, the disk drive 503 and/or the disc drive 506. The optional userinterface output circuitry configured to present information 420 and theoptional user interface input circuitry configured to receive local userinput 425 are not shown explicitly in FIG. 5 and may or may not beincluded therein. Thus, FIG. 5 helps to demonstrate that thecommunications device 400 may be implemented as a server, in addition toa UE as in FIGS. 2A-2B or an access point as in one exampleimplementation of the network component 300.

UEs such as phones, tablet computers, desktop computers or laptopcomputers, are generally configured to connect to terrestrial wirelesscommunication subscriber networks (e.g., 3G, 4G, 5G, etc.) with theexpectation that the UEs are not airborne. For example, users aretypically asked to place their respective UEs into “airplane” modebetween takeoff and landing for commercial flights, which restricts theUEs' capability for connecting to terrestrial wireless communicationsubscriber networks.

For most manned (or piloted) aerial vehicles, typical cruising altitudesand/or speeds make connections to terrestrial wireless communicationsubscriber networks impractical. For example, commercial aircraft mayreach cruising altitudes near 12 km at speeds between 800-1000 km/hr.Instead of relying upon terrestrial wireless communication subscribernetworks to support communications for/with manned aerial vehicles suchas commercial aircraft, most countries allocate a portion of Very HighFrequency (VHF) radio spectrum to define an Airband or Aircraft bandthat is dedicated to radio-navigational communications and/or airtraffic control communications.

Regulatory agencies are increasingly authorizing deployment of unmannedaerial vehicles (UAVs), such as commercial drones. Commercial drones arebeing considered to provide a variety of services, such as packagedelivery, search-and-rescue, monitoring of critical infrastructure,wildlife conservation, flying cameras, surveillance, and so on.Commercial drones may operate at altitudes and speeds that are moresuitable for connections to terrestrial wireless communicationsubscriber networks. For example, in certain environments, commercialdrones may operate at cruising altitudes near 100 m at speeds up to ornear 160 km/h. However, uplink signals from commercial drones that arein-flight generally create more interference to terrestrial basestations compared to “grounded” UEs in a non-flying state, as shown inFIG. 6.

Referring to FIG. 6, a drone 600 is shown at a grounded position,denoted as position 1, and then at an airborne or in-flight position,denoted as position 2. Three base stations (BS1, BS2, BS3) are depictedin FIG. 6. Assume that the drone 600 includes a UE that is attached to(e.g., camped on) BS 2, while UE 1 is attached (e.g., camped on) to BS 1and UE 2 is attached (e.g., camped on) to BS 3. At position 1 on theground, the drone's 600 uplink signals to BS 2 cause a first level ofinterference with respect to BS 1 and BS 3. At position 2 in the air,however, the drone's 600 uplink signals to BS 2 cause a second level ofinterference with respect to BS 1 and BS 3 that is higher than the firstlevel of interference. For example, there are less obstructions betweenthe drone 600 and BS 1 and BS 2 at position 2, which is one reason whythe interference upon BS 1 and BS 3 is higher when the drone 600 is atposition 2.

For some drones (e.g., such as authorized commercial drones), the higherinterference caused by the drone 600 at position 2 is a tradeoff that isdeemed acceptable so as to provide the drone 600 with connectivity whilein-flight. However, some drones (e.g., unauthorized end-user consumerdevices) may not be authorized to connect to one or more terrestrialwireless communication subscriber networks while in-flight, as shown inFIG. 7.

Referring to FIG. 7, assume that drone 700 is a commercial drone that isauthorized to access a terrestrial wireless communication subscribernetwork while in-flight, and is thereby attached to (e.g., camped on) BS1. In an example, the drone 700 may include an integrated terrestrialwireless communication subscriber network module 290 to facilitate itsconnection to BS 1. However, assume that drone 705 is an off-the-shelfconsumer product that is configured for direct line-of-sight (LOS)control by a respective user. However, this user has modified the drone705 by attaching a UE 710. Via a wireless connection to the UE 710 overBS 1, the user of the drone 705 wants to either control the drone 705(e.g., extend the range of the drone 705, etc.) or implement some otheraction (e.g., take pictures or record video using UE 710). The wirelessconnection between UE 710 and BS 1 while UE 710 is in-flight may bedeemed undesirable and unauthorized for certain terrestrial wirelesscommunication subscriber networks, either from a regulatory standpoint(e.g., against governmental regulations) or against operator preference(e.g., the operator of the terrestrial wireless communication subscribernetwork charges a premium for in-flight drone connectivity service, andthe user of UE 710 does not subscribe to this premium service).

Accordingly, various embodiments of the disclosure relate to managingdrone-coupled UEs. As used herein, a drone-coupled UE refers to any UEthat is attached to, or configured to be attached to, a drone,irrespective of whether the drone-coupled UE is actually in-flight.Drone-coupled UEs may include “authorized” drone-coupled UEs (e.g., UEsthat are authorized to be registered with a terrestrial wirelesscommunication subscriber network as a drone-coupled UE, for in-flightcommunicative support, or both) and “unauthorized” drone-coupled UEs(e.g., UEs that unauthorized to be registered with a terrestrialwireless communication subscriber network as a drone-coupled UE, forin-flight communicative support, or both). Moreover, as described abovewith respect to FIG. 2B, the manner in which drone-coupled UEs arecoupled to respective drones via a physical coupling (e.g., a temporaryphysical coupling such as being taped onto the drone, or asemi-permanent coupling such as being integrated or built-into astructure of the drone), a communicative coupling (e.g., thedrone-coupled UE is interfaced communicatively to a controller on thedrone, to permit the drone-coupled UE to engage in flight control of thedrone), or both.

FIGS. 8-9 illustrate procedures by which a drone-coupled capabilityinformation of a drone-coupled UE (e.g., UE 200 of FIGS. 2A-2B) can beconveyed to a network component (e.g., network component 300 of FIG. 3)of a terrestrial wireless communication subscriber network in accordancewith embodiments of the disclosure. In particular, FIG. 8 illustratesoperation of the drone-coupled UE, and FIG. 9 illustrates operation ofthe network component of the terrestrial wireless communicationsubscriber network.

Referring to FIG. 8, at block 800, the drone-coupled UE transmits amessage to a network component of a terrestrial wireless communicationsubscriber network that identifies a drone-coupled capabilityinformation of the drone-coupled UE. More specifically, identificationof the UE as having a drone-coupled capability information is configuredto indicate, to the network component, that the drone-coupled UE iscapable of engaging in a flying state. Similarly, with reference to FIG.9, at block 900, the network component receives a message from adrone-coupled UE that identifies a drone-coupled capability informationof the drone-coupled, and at block 905, the network component determinesthat the drone-coupled UE is capable of engaging in a flying state basedon the received message.

Referring to FIGS. 8-9, in an example, the message conveyance at blocks800 and 900 may be implemented during an initial Attach procedurebetween the drone-coupled UE and a base station of the terrestrialwireless communication subscriber network. For example, the message ofblock 800 may a UE capability signaling message (e.g., new messages suchas drone UE=True or droneFunctions=supported may be defined andsignaled). In another example, one or more new UE categories may bedefined and/or one or more defined UE categories may be reserved fordrone-coupled UEs, and the message of blocks 800 and 900 may identifythe drone-coupled UE as belonging to this reserved UE category. Inanother example, regulators and/or network operators of terrestrialwireless communication subscriber networks (e.g., mobile networkoperators or MNOs) may assign different subscriber IDs and/orcertification IDs to drone-coupled UEs that are authorized for networkaccess. For example, a block of subscriber IDs and/or certification IDsmay be reserved for drone-coupled UEs that are authorized for networkaccess, such that the drone-coupled capability information of adrone-coupled UE can be conveyed to the network component via thedrone-coupled UE's assigned subscriber ID and/or certification IDbelonging to this reserved block.

Referring to FIGS. 8-9, in another example, different regulators and/orMNOs may have different certification criteria and/or procedures forauthorizing network access to drone-coupled UEs. For example,drone-coupled UEs that are authorized for network access may be issuedpredefined keys or identification codes to be used as “certificates”. Inan example, the certificates may be encrypted. The certificates may beprovided to the network component by the UE using Non-Access Stratum(NAS) signaling (e.g., during initial attach procedure, or as adedicated RRC connection reconfiguration procedure later). The networkcomponent (e.g., a core network component) can perform authentication ofthe certificate/code and, if authenticated, deliver such information(e.g. drone authentication success message) to the RAN over 51 signalingor other signaling method.

At block 910, the network component optionally implements adrone-coupled status protocol or a non-drone-coupled status protocol forthe drone-coupled UE based on the determination from block 905. Morespecifically, a determination may be made as to whether drone-coupledservice is authorized generally and/or whether drone-coupled service isauthorized for this particular drone-coupled UE, and service may beprovided (or not provided) accordingly. In an example, if theterrestrial wireless communication subscriber network is not capable ofproviding drone-related service to any drone-coupled UE (e.g., due tolack of drone-coupled service authorization), a service-rejectiondrone-coupled status protocol may be implemented by default. Generally,the non-drone-coupled status protocol refers to normal operation (e.g.,providing the same level of service to the drone-coupled UE as isprovided by the terrestrial wireless communication subscriber network toone or more non-drone-coupled UEs), whereas the drone-coupled statusprotocol refers to implementation of any of a variety of actionsspecifically for drone-coupled UEs that may be expected to fly from timeto time. These actions include, but are not limited to, any combinationof the following:

-   -   Refuse to admit the drone-coupled UE to the terrestrial wireless        communication subscriber network if the drone-coupled UE is        unauthorized for drone-coupled service;    -   Admit the drone-coupled UE to the terrestrial wireless        communication subscriber network for service only while the        drone-coupled UE is not engaged in a flying state based on the        drone-coupled UE being authorized for drone-coupled service and        unauthorized for in-flight service;    -   Admit the drone-coupled UE to the terrestrial wireless        communication subscriber network for a subset of drone-coupled        services while the drone-coupled UE is not engaged in a flying        state, the subset of drone-coupled services including at least        one service that is not available to non-drone-coupled UEs        (i.e., drone-coupled UEs are allocated partial service even when        grounded);    -   Implement a power control scheme for the drone-coupled UE that        is different from power control schemes used for UEs that do not        have drone-coupled capability information; and/or    -   Implement a different charging or pricing scheme for the        drone-coupled UE that is different than charging and/or pricing        schemes used for UEs that do not have drone-coupled capability        information.

FIG. 10A illustrates a process by which a drone-coupled UE conveys amessage indicative of in-flight status in accordance with an embodimentof the disclosure. Referring to FIG. 10A, at block 1000A, thedrone-coupled UE determines whether it is currently engaged in a flyingstate. The determination of block 1000A can occur in a variety of ways.For example, the drone-coupled UE may be communicatively coupled to adrone, which notifies the drone-coupled UE as to whether the drone iscurrently engaged in the flying state (or flying mode), e.g., based onthe status of one or more of its mechanical or electrical components. Inanother example, various measurements (e.g., speed, altitude, etc.) madeindependently by the drone-coupled UE itself may be sufficient for thedrone-coupled UE to determine and/or differentiate between its in-flightor grounded status. In one example, such determination may be based on areference altitude/height threshold, i.e., if the currentaltitude/height of the drone-coupled UE meets the threshold requirement,then the UE is considered to be in a flying state. In one example, thedetermination may be based on the speed of the drone-coupled UE. Inanother example, the determination may be based on the direction inaddition to the speed (i.e., velocity). In another example, thedetermination may be based on the combination of the above. In oneexample, such threshold(s) (e.g., reference height, threshold height,speed, velocity etc.) may be provided by the network to the UE.

Referring to FIG. 10A, at block 1005A, the drone-coupled UE transmits amessage to a network component of a terrestrial wireless communicationsubscriber network that indicates a result of the determination of block1000A. In an example, the message of block 1005A may expressly indicatewhether the drone-coupled UE is currently engaged in the flying state(e.g., via dedicated RRC signaling). For example, the message of block1005A may be a measurement reporting message configured with a newparameter such as nowFlying=True or nowFlying=False. In another example,the drone-coupled UE may have different identifiers for use duringterrestrial mode and flight mode (e.g., different International MobileSubscriber Identities (IMSIs), new Globally Unique Temporary Identifier(GUTI) when the drone-coupled UE is in the flying state, differentcertificate ID/code, etc.). The drone-coupled UE may use these differentIDs to communicate whether the drone-coupled UE is operating in theflying state or a non-flying state.

Referring to FIG. 10A, in another example, the message of block 1005Amay facilitate some action to be taken and/or request that some actionbe taken based on the determination of block 1000A without necessarilyproviding an express indication to the network component as to whetherthe drone-coupled UE is currently engaged in the flying state. Forexample, as described below with respect to FIG. 12A, the drone-coupledUE may request a handover protocol transition in response to a detectedtransition of the drone-coupled UE between the flying state and thenon-flying state. In another example, as described below with respect toFIG. 12A, the drone-coupled UE may request a power control protocoltransition in response to a detected transition of the drone-coupled UEbetween the flying state and the non-flying state. Such requests mayqualify as indirect indications to the network component with regard tothe flight status of the drone-coupled UE (e.g., a request to transitionthe drone-coupled UE to a flying state handover protocol may imply atransition of the drone-coupled UE to the flying state, whereas arequest to transition the drone-coupled UE to a non-flying statehandover protocol may imply a transition of the drone-coupled UE to thenon-flying state, and a request to transition the drone-coupled UE to aflying state power control protocol may imply a transition of thedrone-coupled UE to the flying state, whereas a request to transitionthe drone-coupled UE to a non-flying state power control protocol mayimply a transition of the drone-coupled UE to the non-flying state). Inanother example, the message of block 1005A may facilitate the networkcomponent to perform action(s) to be taken without expressly requestingthat the action(s) be taken.

Referring to FIG. 10A, in another example, the message of block 1005Amay be transmitted to the network component in an event-triggered mannereach time a flight status of the drone-coupled UE changes (e.g., eachtime the drone-coupled UE transitions between the flying state and thenon-flying state). For example, the drone-coupled UE may continuouslymonitor various parameters (e.g., altitude/height, speed, direction ofmovement, etc.) and may transmit the message of block 1005A once one ormore of the measured parameters cross(es) respective threshold(s) (e.g.,which may be provided to the drone-coupled UE by the network). Inanother example, the message of block 1005A may be transmitted to thenetwork component in each instance of a periodic message (e.g., themeasurement reporting message noted above) irrespective of whether theflight status of the drone-coupled UE has changed. Further, the processof FIG. 10A may execute after the process of FIG. 8 in at least oneexample.

FIG. 10B illustrates a process by which a network component receives amessage indicative of in-flight status for a drone-coupled UE inaccordance with an embodiment of the disclosure. The process of FIG. 10Bis implemented at a network component (e.g., network component 300 ofFIG. 3) of a terrestrial wireless communication subscriber network, suchas a RAN component or core network component.

Referring to FIG. 10B, at block 1000B, the network component receives amessage from a drone-coupled UE indicating whether the drone-coupled UEis engaged in a flying state. For example, the message received at block1000B may correspond to the message transmitted by the drone-coupled UEat block 1005A of FIG. 10A.

At block 1005B, the network component optionally implements a flyingstate protocol or a non-flying state protocol for the drone-coupled UEbased on the message received at block 1000B. Generally, the non-flyingstate protocol refers to normal operation (e.g., providing the samelevel of service to the drone-coupled UE as is provided by theterrestrial wireless communication subscriber network to one or morenon-drone-coupled UEs), whereas the flying state protocol refers toimplementation of any of a variety of actions specifically for flyingUEs. These actions include, but are not limited to, any of the actionsdescribed below with respect to 1105A of FIG. 11A.

FIG. 11A illustrates a process of selectively implementing a flyingstate protocol or a non-flying state protocol for a drone-coupled UE inaccordance with an embodiment of the disclosure. The process of FIG. 11Ais implemented at a network component (e.g., network component 300 ofFIG. 3) of a terrestrial wireless communication subscriber network, suchas a RAN component or core network component.

Referring to FIG. 11A, at block 1100A, the network component determineswhether a drone-coupled UE is engaged in a flying state based upon oneor more wireless signals transmitted by the drone-coupled UE. Thedetermination of block 1100A may occur in a variety of ways. In a firstexample, the determination of block 1100A may be based on a message fromthe drone-coupled UE (e.g., the message may correspond to the one ormore wireless signals if the network component is an access networkcomponent, or alternatively the message may be carried on the one ormore wireless signals and then transported to the network component viaa backhaul if the network component is a core network component), suchas an express flying-state notification message received from thedrone-coupled UE (e.g., via dedicated RRC signaling), a request toexecute action(s) that indirectly indicate flying state status ornon-flying state status, inclusion of an identifier that is specific toeither the flying state or the non-flying state, and so on, as describedwith respect to block 1005A of FIG. 10A or block 1000B of FIG. 10B.

In a second example, the determination of block 1100A may be based onother types of messages from the drone-coupled UE, such as measurementreporting of current position data from the drone-coupled UE includingelevation/altitude. For example, the network component may compare acurrent height of the drone-coupled UE with a height threshold todetermine whether or not the drone-coupled UE is engaged in the flyingstate (e.g., if the drone-coupled UE's current height is above theheight threshold, then the flying state is determined for thedrone-coupled UE). A speed of the drone-coupled UE may also be factoredinto the determination. For example, the network component may compare acurrent speed of the drone-coupled UE with a speed threshold todetermine whether or not the drone-coupled UE is engaged in the flyingstate (e.g., if the drone-coupled UE's current speed is above thethreshold speed, then the flying state is determined for thedrone-coupled UE). In another example, the determination may be based ondirection of movement of the drone-coupled UE in addition to the speed(i.e., velocity). In yet another example, the determination may be basedon the combination of the above.

Referring to block 1100A of FIG. 11A, in a third example, thedetermination of block 1100A may be based on internal coordination ofdifferent cells (or base stations) of the terrestrial wirelesscommunication subscriber network. For example, the network component maycompare received power of one or more uplink signals from thedrone-coupled UE as measured at different base stations (e.g., both nearthe drone-coupled UE and far away from the drone-coupled UE). Due toincreased free-space propagation for drone-coupled UEs in the flyingstate, base stations farther away from the drone-coupled UE (e.g.,beyond a distance threshold) measuring the drone-coupled UE's uplinksignals as being strong (e.g., above an uplink signal strengththreshold) may be an indicator that the drone-coupled UE is engaged inthe flying state.

In another example, a mobility pattern of the drone-coupled UE may beevaluated. Drone-coupled UEs engaged in the flying state are expected tohave less frequent handovers (e.g., because environmental changes andpropagation loss over time are more predictable), such that directneighbor cells may be “skipped” during handoff, which does not normallyoccur with respect to UEs that are not flying. This scenario is shown inFIG. 11B, whereby a UE coupled to drone 1100B hands off directly from BSA to BS C (skipping or bypassing “intervening” BS B), while UE 1105B(which is not flying) hands off from BS A to BS B, and then later fromBS B to BS C. It will be appreciated that UE handoffs are determined inpart based upon wireless signal(s) from the UE, such that this exampleof block 1100A is also based in part upon wireless signal(s) from thedrone-coupled UE.

Referring to block 1100A of FIG. 11A, in a fourth example, thedetermination of block 1100A may be based on an estimated angle ofarrival of an uplink signal from the drone-coupled UE. For example, withmulti-antenna technologies, a base station may estimate the angle ofarrival of the received uplink signal from the drone-coupled UE (e.g.,based on one or more angle-of-arrival measurements). The base station(or another network component to which the base station reports theangle of arrival) may then estimate whether a transmitter at thedrone-coupled UE is on the ground or above the ground (i.e., in a flyingstate) by comparing the angle of arrival to a threshold.

At block 1105A, the network component optionally implements a flyingstate protocol or a non-flying state protocol for the drone-coupled UEbased on the determination from block 1100A. Generally, the non-flyingstate protocol refers to normal operation (e.g., providing the samelevel of service to the drone-coupled UE as is provided by theterrestrial wireless communication subscriber network to one or morenon-drone-coupled UEs), whereas the flying state protocol refers toimplementation of any of a variety of actions specifically for flyingUEs. These actions include, but are not limited to, any combination ofthe following:

-   -   Refuse to admit the drone-coupled UE to the terrestrial wireless        communication subscriber network if the drone-coupled UE is        unauthorized for drone-coupled service and/or flying state        service, and/or if the terrestrial wireless communication        subscriber network is unable to provide drone-coupled service        and/or flying state service. In an example, whether or not the        drone-coupled UE is authorized or unauthorized for drone-coupled        service and/or for flying state service can be determined by        querying a Home Subscriber Server (HSS) at the core network of        the terrestrial wireless communication subscriber network. For        example, the subscription information for the drone-coupled UE        may be stored as part of the Universal Integrated Circuit Card        (UICC) or UE configuration. In a further example, new cause        values for connection rejection may be established for notifying        an unauthorized drone-coupled UE with respect to the admission        refusal (e.g., not-A-Drone, droneServiceUnavailable, etc.).        Alternatively or additionally, in another example, new messages        may be defined to signal whether a particular drone-coupled UEs        is authorized for service. Hence, the absence of such a message        may indicate that the particular service is unauthorized for        that particular drone-coupled UE. Such signaling may be based on        dedicated RRC signaling, as discussed below with respect to FIG.        13;    -   Authorize restricted or limited service (e.g., lower        transmission power, lower bandwidth or QoS, etc.) to the        drone-coupled UE to the terrestrial wireless communication        subscriber network if the drone-coupled UE is unauthorized for        drone-coupled service and/or flying state service but it is in a        flying state. Once the drone-coupled UE is determined to no        longer be engaged in the flying state, the unauthorized        drone-coupled UE may then be disconnected from the terrestrial        wireless communication subscriber network. Moreover, the        unauthorized drone-coupled UE may optionally be blacklisted        thereafter from the terrestrial wireless communication        subscriber network altogether for breaching the terms of use for        the unauthorized drone-coupled UE;    -   Authorize service to the drone-coupled UE while assessing a        surcharge to an account of the drone-coupled UE if is not        subscribed for drone-coupled service and/or flying state        service;    -   Implement a power control scheme for the drone-coupled UE in the        flying state that is different from power control schemes used        for drone-coupled UEs that are not in the flying state;    -   Implement a different charging or pricing scheme for the        drone-coupled UE in the flying state that is different than        charging and/or pricing schemes used for drone-coupled UEs that        are not in the flying state; and/or    -   Implement a different handover scheme for the drone-coupled UE        in the flying state that is different than a handover protocol        used for drone-coupled UEs in a non-flying state (e.g.,        discussed in more detail below with respect to FIGS. 12A-12B).

As discussed above with respect to FIGS. 11A-11B, handovercharacteristics associated with an in-flight drone-coupled UE may bedifferent than a grounded or terrestrial UE. For example, the rate atwhich an in-flight drone-coupled UE hands off between base stations maygenerally be less than a typical grounded or terrestrial UE, andin-flight drone-coupled UEs may be more likely to “skip” or bypassintervening base stations, as shown in FIG. 11B. Also, a radio linkfailure (RLF) rate may be lower for in-flight drone-coupled UEs relativeto grounded or terrestrial UEs due to the in-flight drone-coupled UEsbeing more likely to have a direct LOS to their serving base stationand/or more deterministic path loss. In other words, there are fewerenvironmental obstructions at higher altitudes, such that a sudden RLFis less likely for in-flight drone-coupled UEs.

FIG. 12A illustrates an example implementation of the process of FIG.11A in accordance with an embodiment of the disclosure. Referring toFIG. 12A, at block 1200A, the network component determines whether adrone-coupled UE is engaged in a flying state. Block 1200A may beimplemented using any of the methodologies described above with respectto block 1100A of FIG. 11A. At block 1205A, the network componentoptionally implements a flying state handover protocol or a non-flyingstate handover protocol for the drone-coupled UE based on thedetermination from block 1200A. As will be appreciated, block 1205Arepresents an example of block 1100A of FIG. 11A specific to handover.

Referring to FIG. 12A, in an example, the flying state handover protocolmay be configured with new hysteresis and threshold parameters relatedto handover that are customized (or optimized) for expected conditionsassociated with in-flight drone-coupled UEs. Moreover, the process ofFIG. 12A may be repeated each time the network component makes a newdetermination as to whether the drone-coupled UE is engaged in theflying state or the non-flying state.

In an example, to avoid a “ping-ponging” effect while the drone-coupledUE is actively connected to the terrestrial wireless communicationsubscriber network (e.g., RRC Connected mode), a different set ofthresholds for characterizing a drone-coupled UE as being in the flyingstate or the non-flying state may be used for the purpose of making ahandover protocol switching decision than for other flying/non-flyingstate determinations. In other words, the determination of block 1200Amay be configured to provide a higher degree of confidence that thedrone-coupled UE has truly switched between the flying state and thenon-flying state before the handover protocol is authorized to beswitched. For example, assume that a “default” minimum height thresholdto qualify for the flying state is normally 30 m. Now further assumethat a drone-coupled UE is determined to be in a non-flying state, suchthat the network component is implementing a non-flying state handoverprotocol for the drone-coupled UE. In this case, the minimum heightthreshold for implementing a handover protocol transition may beaugmented (e.g., to 40 m, 50 m, etc.) to avoid ping-ponging. So,different thresholds and/or parameters may be utilized for assessinggrounded or in-flight status of a drone-coupled UE in certaincircumstances. This way, a brief “dip” (or altitude drop) of thedrone-coupled while in-flight will not trigger a handover protocolchange, and likewise a false start (or quick altitude increase followedby a return to ground) will not trigger a handover protocol change. In afurther example, the various thresholds and/or parameters used to assessgrounded or in-flight status of a drone-coupled UE may be configurable(e.g., using dedicated RRC signaling or a broadcast SIB), either for alldrone-coupled UEs or for particular groups or classes of drone-coupledUEs.

In a further example, while the drone-coupled UE is actively connectedto the terrestrial wireless communication subscriber network (e.g., RRCConnected mode), a drone-coupled UE may provide assistance informationto the network component that is configured to implicitly or expresslyrequest a handover protocol transition (e.g., as described above withrespect to block 1005A of FIG. 10A or block 1000B of FIG. 10B). In anexample, the assistance information may be based on a current channeland/or interference environment of the drone-coupled UE as perceived viaits own measurements. For example, the drone-coupled UE may transmit theassistance information to request a handover protocol transition inresponse to a determination that the drone-coupled UE has transitionedbetween the flying state and the non-flying state (e.g., thedrone-coupled UE may start seeing a lot more strong neighbor basestations and determine that the drone-coupled UE is likely in-flight,such that the flying state handover protocol is now preferred, whichtriggers the request to be sent). Accordingly, the status of thedrone-coupled UE as being flying or grounded at block 1200A may beinferred from a message from the drone-coupled UE that requests aparticular handover protocol, which may occur as described above withrespect to block 1005A of FIG. 10A or block 1000B of FIG. 10B in oneexample.

Referring to FIG. 12A, it is possible that a drone-coupled UE can beengaged in the flying state while still being in an Idle mode (e.g., RRCIdle) with respect to the terrestrial wireless communication subscribernetwork. For example, the drone-coupled UE may be controlled via adifferent network type altogether (e.g., a satellite network, a directLOS control system, a different terrestrial wireless communicationsubscriber network, etc.). In these instances, the network componentwill consider the drone-coupled UE to be Idle even while thedrone-coupled UE is engaged in the flying state. These “idle and flying”drone-coupled UEs may be controlled by some mechanism other than theterrestrial wireless communication subscriber network, but may stillwant to connect to the terrestrial wireless communication subscribernetwork from time to time (e.g., to start transmitting audio and/orvideo data).

For these reasons, in at least one embodiment, different flying statehandover protocols may be established based on whether an in-flightdrone-coupled UE is in “Connected” mode or “Idle” mode with respect tothe terrestrial wireless communication subscriber network.

In Idle mode, a Tracking Area Identifier (TAI) list may be used todetermine a general area where the Idle drone-coupled UE is located. Thesize of the TAI list determines the size of a paging radius for the Idledrone-coupled UE in the event that the Idle drone-coupled UE needs to bepaged by the terrestrial wireless communication subscriber network. Asnoted above, unlike UEs on the ground, in-flight drone-coupled UEs maybe more likely of reselecting cells from different TAI lists due to thedifferent mobility patterns of the in-flight drone-coupled UEs. In otherwords, more neighbor cells will generally be in serving range ofin-flight drone-coupled UEs, such that in-flight drone-coupled UEs havemore options in terms of neighbor cell reselection. Accordingly, theflying state handover protocol may include a larger paging radius and/ora cell reselection list encompassing cells in a larger area relative tothe non-flying state handover protocol.

Consider for instance a TAI list 1 (or “TAI1”) that contains cells {1,2, 3, 4}, whereas a TAI list 2 (or “TAI2”) that contains cells {5, 6, 7,8}. A terrestrial or grounded Idle UE may perform a Tracking Area Update(TAU) only when the Idle UE goes from cell 4 to 5, for example, whereasan Idle in-flight drone-coupled UE while camped on cell 2 may also seecell 6 or 7 as suitable cell. This may trigger more frequent TAUs forthe Idle in-flight drone-coupled UE if only TAU_or TAI2 are allocated tothe Idle in-flight drone-coupled UE. On the other hand, if the networkcomponent (e.g., an MME) allocates TAI1+TAI2 (union set of the two, forexample, which is {1, 2, 3, 4, 5, 6, 7, 8} in above example) as a TAIlist to the Idle in-flight drone-coupled UE, the frequency of reporting(e.g., TAUs) may be reduced from the Idle in-flight drone-coupled UE.Accordingly, the flying state handover protocol may include one or moredifferent location reporting parameters (e.g., reduced locationreporting) while in Idle mode relative than the non-flying statehandover protocol.

In an LTE-specific example, an eNB may need to report whether the Idledrone-coupled UE is airborne (or engaged in the flying state, i.e.,in-flight) to the MME on a periodic basis so that the MME can update thecorresponding TAI list for the Idle drone-coupled UE. In an example, theeNB may report measurement information related to the Idle drone-coupledUE to the MME (e.g., current height/altitude), or alternatively mayexpressly indicate to the MME whether the Idle drone-coupled UE isengaged in the flying state or the non-flying state. In an example wherethe eNB reports the height of the Idle drone-coupled UE to the MME, theMME may determine whether the Idle drone-coupled UE is flying or not bycomparing a reported height of the Idle drone-coupled UE to a heightthreshold. In a further example, one or more new threshold parametersmay be introduced for Idle mode reselection for in-flight drone-coupledUEs. For example, a different value for S_(IntraSearchP) can beimplemented for in-flight drone-coupled UEs as part of the flying statehandover protocol relative to non-flying UEs. While this particularexample is LTE-specific, it will be appreciated that other embodimentscan be directed to any wireless communications scheme (e.g., 5G NR,etc.).

FIG. 12B illustrates a more detailed implementation of the process ofFIG. 12A in accordance with an embodiment of the disclosure. Referringto FIG. 12B, at block 1200B, a network component of a terrestrialwireless communication subscriber network determines a drone-coupled tobe engaged in a flying state. At block 1205B, the network componentdetermines whether the drone-coupled UE is in an “Idle” or “Connected”mode with respect to the terrestrial wireless communication subscribernetwork. If the network component determines that the drone-coupled UEis in an “Idle” mode with respect to the terrestrial wirelesscommunication subscriber network at block 1205B, the network componentimplements an “Idle” flying state handover protocol for thedrone-coupled UE at block 1210B. Otherwise, if the network componentdetermines that the drone-coupled UE is in a “Connected” mode withrespect to the terrestrial wireless communication subscriber network atblock 1205B, the network component implements a “Connected” flying statehandover protocol for the drone-coupled UE at block 1215B.

Referring to FIG. 12B, at block 1220B, the network component determineswhether any status change has occurred that is sufficient to trigger ahandover protocol transition for the drone-coupled UE. Examples ofstatus changes that are sufficient to trigger a handover protocoltransition for the drone-coupled UE may include a transition of thedrone-coupled UE from Connected mode to Idle mode (or vice versa), orfrom the flying state to the non-flying state. While not shown expresslyin FIG. 12B, if the network component determines that no status changehas occurred that is sufficient to trigger a handover protocoltransition for the drone-coupled UE at block 1220B, the networkcomponent maintains the drone-coupled UE in its current handoverprotocol. If the network component determines that the drone-coupled UEhas transitioned between Connected mode and Idle mode while still beingengaged in the flying state at block 1220B, the process returns to block1205B and a different flying state handover protocol is implemented forthe drone-coupled UE. If the network component determines that thedrone-coupled UE has transitioned to the non-flying state at block1220B, the network component switches the drone-coupled UE to thenon-flying state handover protocol at 1225B. The process then returns toblock 1200B, where the network component monitors the drone-coupled UEto determine whether the drone-coupled UE re-engages the flying state.

FIG. 13 illustrates a process by which a network component (e.g., a RANcomponent or core network component) of a terrestrial wirelesscommunication subscriber network conveys an available support status fordrone-related service in accordance with an embodiment of thedisclosure. At block 1300, the network component configures a messagethat indicates a degree to which the terrestrial wireless communicationsubscriber network supports service to one or more drone-coupled UEs. Atblock 1305, the network component transmits the configured message.

Referring to FIG. 13, the message configured at block 1300 andtransmitted at block 1305 may be either a dedicated (e.g., unicast)message that is targeted to a particular target UE, or a broadcastmessage that is targeted more generally to UEs being served by theterrestrial wireless communication subscriber network.

Referring to FIG. 13, in an example where the message transmitted atblock 1305 is a dedicated (or unicast) message, the message at block1305 may be implemented via dedicated Radio Resource Control (RRC)signaling using a new Information Element (IE) and/or new field(s) inexisting IE(s):

RRCConnectionSetupComplete-vXXYY-IEs ::= SEQUENCE { uav-Services-rXX  ENUMERATED {supported} OPTIONAL, nonCriticalExtension   SEQUENCE { } OPTIONAL  }

Referring to FIG. 13, in an example where the message transmitted atblock 1305 is a broadcast message, the message at block 1305 may bebroadcast via a System Information Block (SIB) message. In a furtherexample, the support of UEs coupled to certain types of UAVs may berestricted/allowed by reusing an Access Class Barring (ACB) methodwherein the information of allowed/barred access classes is broadcastvia a SIB. In a further example, certain terrestrial wirelesscommunication subscriber networks may support service to drone-coupledUEs while other terrestrial wireless communication subscriber networksdo not. In this case, the message at block 1305 may simply indicatewhether or not drone-coupled UEs are supported at all, e.g. as a “flag”.In an example, some drone-coupled UEs may still access the terrestrialwireless communication subscriber networks in “barred” terrestrialwireless communication subscriber networks, but only using “normal”procedures that do not involve their “drone-coupled” statuses (e.g., solong as the drone-coupled UEs are positioned terrestrially, or grounded,and do not actually engage in the flying state).

However, the barring of drone-related service could also be morenuanced. For example, the ACB may depend on the traffic type ordrone-classes. For example, a drone-coupled UE that uses the terrestrialwireless communication subscriber network for video streaming may bebarred, but one that uses the terrestrial wireless communicationsubscriber network for telemetry may not. Alternatively or additionally,a drone-coupled UE may belong to different drone-classes depending onthe services it needs, out of which some services may be barred whileothers are not. In such case, the drone-coupled UE may want to initiatelimited-service drone operation. As examples, the barring criteria maybe such as:

-   -   Bar all drone-coupled UEs,    -   Bar all drone-coupled UEs that are engaged in the flying state,        or    -   Bar all drone-coupled UEs that are engaged in the flying state        while capturing videos that do not relate to a public service        function.

FIG. 14 illustrates a process by which a drone-coupled UE determineswhether to request service (and/or how much service to request) from aterrestrial wireless communication subscriber network in accordance withan embodiment of the disclosure. At block 1400, the drone-coupled UEreceives a message that indicates a degree to which a terrestrialwireless communication subscriber network supports service to one ormore drone-coupled UEs. For example, the message received at block 1400may correspond to the message transmitted at block 1305 of FIG. 13(e.g., via a unicast protocol such as dedicated RRC signaling, or abroadcast protocol such as a flag in a SIB or ACB via a SIB). At block1405, the drone-coupled UE selectively requests service from theterrestrial wireless communication subscriber network based in part uponthe received message. In particular, at block 1405, the drone-coupled UEmay compare the degree to which the terrestrial wireless communicationsubscriber network supports service (e.g., either to the drone-coupledUE specifically or to a class of drone-coupled UE to which thedrone-coupled UE belongs) to its own service requirement to determinehow much (if any) service to request from the terrestrial wirelesscommunication subscriber network.

FIG. 15 illustrates an example implementation of the process of FIG. 14in accordance with an embodiment of the disclosure. In particular, FIG.15 illustrates a broadcast-specific example of the drone-serviceavailability message described above in FIG. 14, although it will beappreciated that other embodiments may be directed to dedicated (orunicast) implementations of the drone-service availability message.

Referring to FIG. 15, assume that a drone-coupled UE is connected to aterrestrial wireless communication subscriber network in a non-flyingstate (e.g., terrestrial mode) and wants to initiate flight mode thatrequires in-flight drone service from the terrestrial wirelesscommunication subscriber network. At block 1500 (e.g., as in 1400 ofFIG. 14), the drone-coupled UE acquires and decodes a SIB correspondingto drone access control. At block 1505, the drone-coupled UE determinesif the SIB indicates whether the drone-coupled UE is barred fromin-flight drone service from the terrestrial wireless communicationsubscriber network. If so, at block 1510, the drone-coupled UE does notinitiate flight mode and instead continues in terrestrial mode. However,if the drone-coupled UE determines that the SIB indicates thedrone-coupled UE is not barred from in-flight drone service from theterrestrial wireless communication subscriber network at block 1505,then the drone-coupled UE initiates a transition into flight mode atblock 1515.

FIG. 16 illustrates an example implementation of the process of FIG. 14in accordance with another embodiment of the disclosure. FIG. 16 issimilar to FIG. 15, but FIG. 16 relates to an implementation thatinvolves more nuanced barring rules for drone-related service.

Referring to FIG. 16, assume that a drone-coupled UE is connected to aterrestrial wireless communication subscriber network in a non-flyingstate (e.g., terrestrial mode) and wants to initiate flight mode usingone or more particular in-flight drone services from the terrestrialwireless communication subscriber network. At block 1600 (e.g., as in1400 of FIG. 14), the drone-coupled UE acquires and decodes a SIBcorresponding to drone access control. At block 1605, the drone-coupledUE determines if the SIB indicates whether the drone-coupled UE isbarred from each of the one or more in-flight drone services from theterrestrial wireless communication subscriber network that are desiredby the drone-coupled UE. If so, at block 1610, the drone-coupled UE doesnot initiate flight mode and instead continues in terrestrial mode.However, if the drone-coupled UE determines that the SIB indicates thedrone-coupled UE is not barred from each of the one or more in-flightdrone services from the terrestrial wireless communication subscribernetwork that are desired by the drone-coupled UE at block 1605, then thedrone-coupled UE determines whether the SIB indicates the drone-coupledUE is barred from any of the one or more in-flight drone services fromthe terrestrial wireless communication subscriber network that aredesired by the drone-coupled UE at block 1615.

Referring to FIG. 16, if the drone-coupled UE determines that each ofits desired one or more in-flight drone services is available at block1615, then “full-service” flight mode is initiated at block 1620.Alternatively, if the drone-coupled UE determines that less than all ofits desired one or more in-flight drone services are available at block1615, then “limited-service” flight mode is initiated at block 1625using the available in-flight drone service(s).

As will be appreciated from a review of FIGS. 15-16, the drone-coupledUE may initiate a transition of the drone-coupled UE into a flying stateif the indicated degree to which the terrestrial wireless communicationsubscriber supports service to drone-coupled UEs is above a threshold,and the drone-coupled UE may delay initiation of the transition of thedrone-coupled UE into the flying state if the indicated degree to whichthe terrestrial wireless communication subscriber supports service todrone-coupled UEs is not above the threshold.

With respect to FIGS. 13-16, an embodiment is directed to a method ofoperating a network component of a terrestrial wireless communicationsubscriber network, comprising configuring a message that indicates adegree to which the terrestrial wireless communication subscribersupports service to one or more drone-coupled UEs, and transmitting theconfigured message. In an example, the transmitting transmits theconfigured message as a dedicated message that targets a singledrone-coupled UE. In a further example, the dedicated message isimplemented via dedicated RRC signaling using at least one IE. In afurther example, the transmitting transmits the configured message as abroadcast message (e.g., via a SIB and/or via an ACB protocol) thattargets multiple UEs. In a further example, the indicated degree towhich the terrestrial wireless communication subscriber supports serviceto the one or more drone-coupled UEs is one of barring all drone-coupledUEs, barring all drone-coupled UEs engaged in a flying state, and/orbarring all drone-coupled UEs engaged in the flying state whilecapturing videos that do not relate to a public service function. Withrespect to FIGS. 13-16, another embodiment is directed to a method ofoperating a drone-coupled UE, receiving a message that indicates adegree to which a terrestrial wireless communication subscriber networksupports service to one or more drone-coupled UEs, selectivelyrequesting service from the terrestrial wireless communicationsubscriber network based in part upon the received message. In anexample, the received message is a dedicated message that individuallytargets the drone-coupled UE. In a further example, the dedicatedmessage is implemented via dedicated RRC signaling using at least oneIE. In a further example, the received message as a broadcast message(e.g., via a SIB and/or via an ACB protocol) that targets multiple UEs.In a further example, the indicated degree to which the terrestrialwireless communication subscriber supports service to the one or moredrone-coupled UEs is one of barring all drone-coupled UEs, barring alldrone-coupled UEs engaged in a flying state, and/or barring alldrone-coupled UEs engaged in the flying state while capturing videosthat do not relate to a public service function. In a further example,the drone-coupled UE initiates a transition of the drone-coupled UE intoa flying state if the indicated degree to which the terrestrial wirelesscommunication subscriber supports service to the one or moredrone-coupled UEs is above a threshold, and delays initiation of thetransition of the drone-coupled UE into the flying state if theindicated degree to which the terrestrial wireless communicationsubscriber supports service to the one or more drone-coupled UEs is notabove the threshold.

Those of skill in the art will appreciate that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a DSP, an ASIC, a FPGA orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general purpose processor maybe a microprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The methods, sequences and/or algorithms described in connection withthe embodiments disclosed herein may be embodied directly in hardware,in a software module executed by a processor, or in a combination of thetwo. A software module may reside in RAM memory, flash memory, ROMmemory, EPROM memory, EEPROM memory, registers, hard disk, a removabledisk, a CD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal (e.g., UE). In thealternative, the processor and the storage medium may reside as discretecomponents in a user terminal.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes CD, laser disc, optical disc,digital versatile disc (DVD), floppy disk and blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media.

While the foregoing disclosure shows illustrative embodiments of thedisclosure, it should be noted that various changes and modificationscould be made herein without departing from the scope of the disclosureas defined by the appended claims. The functions, steps and/or actionsof the method claims in accordance with the embodiments of thedisclosure described herein need not be performed in any particularorder. Furthermore, although elements of the disclosure may be describedor claimed in the singular, the plural is contemplated unless limitationto the singular is explicitly stated.

What is claimed is:
 1. A method of operating a drone-coupled userequipment (UE), comprising: transmitting a message to a networkcomponent of a terrestrial wireless communication subscriber networkthat identifies a drone-coupled capability information of thedrone-coupled UE, the drone-coupled capability information beingconfigured to indicate, to the network component, that the drone-coupledUE is capable of engaging in a flying state.
 2. The method of claim 1,wherein the transmitting occurs during an Attach procedure between thedrone-coupled UE and the terrestrial wireless communication subscribernetwork.
 3. The method of claim 2, wherein the message is a UEcapability signaling message that indicates the drone-coupled capabilityinformation of the drone-coupled UE.
 4. The method of claim 1, whereinthe transmitting occurs during a reconfiguration procedure that occursafter an Attach procedure between the drone-coupled UE and theterrestrial wireless communication subscriber network.
 5. The method ofclaim 1, wherein the message identifies a UE category that is reservedfor drone-coupled UEs.
 6. The method of claim 1, wherein the messageincludes a subscriber identifier (ID) and/or a certification ID that isreserved for drone-coupled UEs.
 7. The method of claim 1, wherein themessage includes a predefined key or identification code usingNon-Access Stratum (NAS) signaling.
 8. The method of claim 1, whereinthe network component is an access network component of the terrestrialwireless communication subscriber network.
 9. The method of claim 1,wherein the network component is a core network component of theterrestrial wireless communication subscriber network.
 10. A method ofoperating a network component of a terrestrial wireless communicationsubscriber network, comprising: receiving a message from a drone-coupleduser equipment (UE) that identifies a drone-coupled capabilityinformation of the drone-coupled UE; and determining that thedrone-coupled UE is capable of engaging in a flying state based on thereceived message.
 11. The method of claim 10, wherein the receivingoccurs during an Attach procedure between the drone-coupled UE and theterrestrial wireless communication subscriber network.
 12. The method ofclaim 11, wherein the message is a UE capability signaling message thatindicates the drone-coupled capability information of the drone-coupledUE.
 13. The method of claim 10, wherein the receiving occurs during areconfiguration procedure that occurs after an Attach procedure betweenthe drone-coupled UE and the terrestrial wireless communicationsubscriber network.
 14. The method of claim 10, wherein the messageidentifies a UE category that is reserved for drone-coupled UEs.
 15. Themethod of claim 10, wherein the message includes a subscriber identifier(ID) and/or a certification ID that is reserved for drone-coupled UEs.16. The method of claim 10, wherein the message includes a predefinedkey or identification code using Non-Access Stratum (NAS) signaling. 17.The method of claim 10, wherein the network component is an accessnetwork component of the terrestrial wireless communication subscribernetwork.
 18. The method of claim 10, wherein the network component is acore network component of the terrestrial wireless communicationsubscriber network.
 19. The method of claim 10, further comprising:implementing a drone-coupled status protocol or a non-drone-coupledstatus protocol based on the determining.
 20. The method of claim 19,wherein the non-drone-coupled status protocol corresponds to theterrestrial wireless communication subscriber network providing the samelevel of service to the drone-coupled UE as is provided by theterrestrial wireless communication subscriber network to one or morenon-drone-coupled UEs.
 21. The method of claim 19, wherein thedrone-coupled status protocol includes: refusing to admit thedrone-coupled UE to the terrestrial wireless communication subscribernetwork based on the drone-coupled UE being unauthorized fordrone-coupled service.
 22. The method of claim 19, wherein thedrone-coupled status protocol includes: refusing to admit thedrone-coupled UE to the terrestrial wireless communication subscribernetwork based on the terrestrial wireless communication subscribernetwork being unable to provide and/or unauthorized to providedrone-coupled service to any drone-coupled UE.
 23. The method of claim19, wherein the drone-coupled status protocol includes: admitting thedrone-coupled UE to the terrestrial wireless communication subscribernetwork for a subset of drone-coupled services while the drone-coupledUE is not engaged in a flying state, the subset of drone-coupledservices including at least one service that is not available tonon-drone-coupled UEs.
 24. The method of claim 19, wherein thedrone-coupled status protocol includes: implementing a power controlscheme for the drone-coupled UE that is different from power controlschemes used for non-drone-coupled UEs.
 25. The method of claim 19,wherein the drone-coupled status protocol includes: implementing acharging or pricing scheme for the drone-coupled UE that is differentthan charging and/or pricing schemes used for non-drone-coupled UEs. 26.A drone-coupled user equipment (UE), comprising: a memory; at least oneprocessor coupled to the memory and a wireless communications interfaceand configured to: transmit a message to a network component of aterrestrial wireless communication subscriber network that identifies adrone-coupled capability information of the drone-coupled UE, thedrone-coupled capability information being configured to indicate, tothe network component, that the drone-coupled UE is capable of engagingin a flying state.
 27. The drone-coupled UE of claim 26, wherein themessage is a UE capability signaling message that indicates thedrone-coupled capability information of the drone-coupled UE, whereinthe message identifies a UE category that is reserved for drone-coupledUEs, wherein the message includes a subscriber identifier (ID) and/or acertification ID that is reserved for drone-coupled UEs, and/or whereinthe message includes a predefined key or identification code usingNon-Access Stratum (NAS) signaling.
 28. A network component of aterrestrial wireless communication subscriber network, comprising: amemory; and at least one processor coupled to the memory and at leastone communications interface and configured to: receive a message from adrone-coupled user equipment (UE) that identifies a drone-coupledcapability information of the drone-coupled UE; and determine that thedrone-coupled UE is capable of engaging in a flying state based on thereceived message.
 29. The network component of claim 28, wherein themessage is a UE capability signaling message that indicates thedrone-coupled capability information of the drone-coupled UE, whereinthe message identifies a UE category that is reserved for drone-coupledUEs, wherein the message includes a subscriber identifier (ID) and/or acertification ID that is reserved for drone-coupled UEs, and/or whereinthe message includes a predefined key or identification code usingNon-Access Stratum (NAS) signaling.
 30. The network component of claim28, wherein the at least one processor is configured to implement adrone-coupled status protocol or a non-drone-coupled status protocolbased on the determination.